<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>&lt;%GLibFileError&gt;: </title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.2">
<link rel="home" href="index.html" title="">
<link rel="up" href="ch01.html" title="GLib">
<link rel="prev" href="re15.html" title="&lt;%GLibErrorType&gt;">
<link rel="next" href="re17.html" title="&lt;%GLibFileSetContentsFlags&gt;">
<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><img src="up-insensitive.png" width="16" height="16" border="0"></td>
<td><a accesskey="p" href="re15.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="re17.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="id-1.1.17"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2>&lt;%GLibFileError&gt;</h2>
<p>&lt;%GLibFileError&gt;</p>
</div>
<div class="refsect1">
<a name="id-1.1.17.2"></a><h2>Description</h2>
<p>Values corresponding to <em class="parameter"><code>errno</code></em> codes returned from file operations
on UNIX. Unlike <em class="parameter"><code>errno</code></em> codes, GFileError values are available on
all systems, even Windows. The exact meaning of each code depends
on what sort of file operation you were performing; the UNIX
documentation gives more details. The following error code descriptions
come from the GNU C Library manual, and are under the copyright
of that manual.
</p>
<p>It's not very portable to make detailed assumptions about exactly
which errors will be returned from a given operation. Some errors
don't occur on some systems, etc., sometimes there are subtle
differences in when a system will report a given error, etc.</p>
</div>
<div class="refsect1">
<a name="id-1.1.17.3"></a><h2>Members</h2>
<div class="refsect2">
<a name="id-1.1.17.3.2"></a><h3>exist</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_EXIST</code></span></em></p>
<p>Operation not permitted; only the owner of
    the file (or other resource) or processes with special privileges
    can perform the operation.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.3"></a><h3>isdir</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_ISDIR</code></span></em></p>
<p>File is a directory; you cannot open a directory
    for writing, or create or remove hard links to it.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.4"></a><h3>acces</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_ACCES</code></span></em></p>
<p>Permission denied; the file permissions do not
    allow the attempted operation.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.5"></a><h3>nametoolong</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NAMETOOLONG</code></span></em></p>
<p>Filename too long.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.6"></a><h3>noent</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NOENT</code></span></em></p>
<p>No such file or directory. This is a "file
    doesn't exist" error for ordinary files that are referenced in
    contexts where they are expected to already exist.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.7"></a><h3>notdir</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NOTDIR</code></span></em></p>
<p>A file that isn't a directory was specified when
    a directory is required.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.8"></a><h3>nxio</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NXIO</code></span></em></p>
<p>No such device or address. The system tried to
    use the device represented by a file you specified, and it
    couldn't find the device. This can mean that the device file was
    installed incorrectly, or that the physical device is missing or
    not correctly attached to the computer.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.9"></a><h3>nodev</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NODEV</code></span></em></p>
<p>The underlying file system of the specified file
    does not support memory mapping.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.10"></a><h3>rofs</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_ROFS</code></span></em></p>
<p>The directory containing the new link can't be
    modified because it's on a read-only file system.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.11"></a><h3>txtbsy</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_TXTBSY</code></span></em></p>
<p>Text file busy.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.12"></a><h3>fault</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_FAULT</code></span></em></p>
<p>You passed in a pointer to bad memory.
    (GLib won't reliably return this, don't pass in pointers to bad
    memory.)</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.13"></a><h3>loop</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_LOOP</code></span></em></p>
<p>Too many levels of symbolic links were encountered
    in looking up a file name. This often indicates a cycle of symbolic
    links.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.14"></a><h3>nospc</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NOSPC</code></span></em></p>
<p>No space left on device; write operation on a
    file failed because the disk is full.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.15"></a><h3>nomem</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NOMEM</code></span></em></p>
<p>No memory available. The system cannot allocate
    more virtual memory because its capacity is full.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.16"></a><h3>mfile</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_MFILE</code></span></em></p>
<p>The current process has too many files open and
    can't open any more. Duplicate descriptors do count toward this
    limit.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.17"></a><h3>nfile</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NFILE</code></span></em></p>
<p>There are too many distinct file openings in the
    entire system.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.18"></a><h3>badf</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_BADF</code></span></em></p>
<p>Bad file descriptor; for example, I/O on a
    descriptor that has been closed or reading from a descriptor open
    only for writing (or vice versa).</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.19"></a><h3>inval</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_INVAL</code></span></em></p>
<p>Invalid argument. This is used to indicate
    various kinds of problems with passing the wrong argument to a
    library function.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.20"></a><h3>pipe</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_PIPE</code></span></em></p>
<p>Broken pipe; there is no process reading from the
    other end of a pipe. Every library function that returns this
    error code also generates a 'SIGPIPE' signal; this signal
    terminates the program if not handled or blocked. Thus, your
    program will never actually see this code unless it has handled
    or blocked 'SIGPIPE'.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.21"></a><h3>again</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_AGAIN</code></span></em></p>
<p>Resource temporarily unavailable; the call might
    work if you try again later.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.22"></a><h3>intr</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_INTR</code></span></em></p>
<p>Interrupted function call; an asynchronous signal
    occurred and prevented completion of the call. When this
    happens, you should try the call again.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.23"></a><h3>io</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_IO</code></span></em></p>
<p>Input/output error; usually used for physical read
   or write errors. i.e. the disk or other physical device hardware
   is returning errors.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.24"></a><h3>perm</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_PERM</code></span></em></p>
<p>Operation not permitted; only the owner of the
   file (or other resource) or processes with special privileges can
   perform the operation.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.25"></a><h3>nosys</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_NOSYS</code></span></em></p>
<p>Function not implemented; this indicates that
   the system is missing some functionality.</p>
</div>
<div class="refsect2">
<a name="id-1.1.17.3.26"></a><h3>failed</h3>
<p class="remark"><em><span class="remark">alias <code class="code">G_FILE_ERROR_FAILED</code></span></em></p>
<p>Does not correspond to a UNIX error code; this
   is the standard "failed for unspecified reason" error code present
   in all <span class="type">GError</span> error code enumerations. Returned if no specific
   code applies.</p>
</div>
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.33.1</div>
</body>
</html>
